Stop reloading Tailwind during morph navigation#704
Closed
Conversation
srid
force-pushed
the
codex/fix-e2e-morph-calendar
branch
from
9c846cc to
f6e4679
Compare
srid
changed the title
srid
force-pushed
the
codex/fix-e2e-morph-calendar
branch
from
f6e4679 to
3894bac
Compare
srid
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Morph navigation no longer re-executes the Tailwind browser compiler on every route switch. The live-server Tailwind CDN script installs a document-wide
MutationObserver; Ema's generic script reloader was running that script again after morphs, multiplying observers and making the calendar route wait behind repeated Tailwind rebuild work before the test harness could observe navigation completion.The fix marks the live Tailwind CDN script with Ema's existing
data-ema-skip="true"contract. The original Tailwind observer remains active and still sees morphed DOM changes; it just is not duplicated byreloadScripts.Validation run locally:
just e2e-morph- 42 passedjust e2e-live- 42 passedjust e2e-static- 39 passed, 3 skippedGenerated by Codex (model
gpt-5).